Providing quality of service based on bandwidth

ABSTRACT

A method for determining a Quality of Service (QoS) policy can be based on requested bandwidth. The method may initially receive a connection request which includes a requested bandwidth that corresponds to an application. The method may then determine a policy for an application data flow associated with the application based on the connection request. A bandwidth designation, which is based on the requested bandwidth, may be assigned to the application data flow based on the determined policy. Finally, the policy and the bandwidth designation may be provided so that a bearer can be assigned.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of application Ser. No. 14/158,061,filed Jan. 17, 2014, the contents of which are hereby incorporatedherein by reference in its entirety.

BACKGROUND

Mobile wireless communication systems have finite resources which aretypically shared among users and a variety of services. Different typesof applications using these services can place varied demands on thewireless network. To address these demands, Quality of Service (QoS)techniques efficiently partition available network resources to providesufficient service for all the applications. Conventional QoS techniquesrely on relative priorities which are based on QoS Class Identifiers(QCIs) for scheduling packets. However, such techniques can result ininadequate bandwidth for some applications.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of an exemplary network which may provideQuality of Service (QoS) based on application resource requirements;

FIG. 2 is a block diagram showing exemplary components of a base stationaccording to an embodiment;

FIG. 3 is a block diagram showing exemplary components of a mobiledevice according to an embodiment;

FIG. 4 is a block diagram showing exemplary components of a serveraccording to an embodiment;

FIG. 5A is a block diagram illustrating the operation of an exemplaryscheduler which allocates resources based on requested bandwidth;

FIG. 5B is a block diagram illustrating the operation of an exemplaryscheduler which allocates resources based on wireless channelconditions;

FIG. 6 is a signal flow diagram depicting exemplary messages exchangedbetween networking elements;

FIG. 7 is a flow chart showing an exemplary process for providing a QoSpolicy based on bandwidth;

FIG. 8 is a flow chart showing an exemplary process for QoS resourceallocation based on bandwidth; and

FIG. 9 is a flowchart showing an exemplary process for receivingresource blocks allocated based on bandwidth.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

The following detailed description refers to the accompanying drawings.The same reference numbers in different drawings may identify the sameor similar elements. The following detailed description does not limitthe invention.

Embodiments described herein are directed to approaches for providingQuality of Service (QoS) which may be based on resources requested foran application, and/or wireless channel resources available to a mobiledevice that hosts the application. QoS prioritization for conventionalnon-Guaranteed Bit Rate (GBR) traffic may be based on relative priorityspecified using QoS Class Identifiers (QCIs). Using the QCI values,application data flows may be divided into different service categoriesbased on their relative priority. Because the service categories onlyprovide a coarse differentiation between their offered services,different applications having widely varying resource requirements maybe placed into the same service category. As a result, within a givenservice category, some applications may not receive adequate resourcesfor proper operation when “competing” with less resource intensiveapplications. For example, buffered video streaming and email can beclassified under the same QCI, and thus receive the same level ofservice, even though buffered video streaming can require significantlymore bandwidth than email.

Embodiments presented herein can address such discrepancies amongdifferent application data flows (which have the same QCI value) andthus provide finer granularity service differentiation among differentapplications for a given user. Alternate embodiments may offer finergranularity service differentiation among similar application data flowsamong separate users, wherein the separate users are associated withdifferent wireless channel conditions. Thus, various embodiments aredescribed below provide “application fairness,” and thus may offer finergranularity service differentiation than existing QoS approaches.

FIG. 1 is a block diagram of an exemplary network 100 which may provideQoS based on application resource requirements such as bandwidth.Network 100 may include wireless network 105, Wide Area Network (WAN)160, and content provider(s) 170. While wireless network 105 is shown inthe context of an Long Term Evolution (LTE) network, it should beappreciated that embodiments presented herein may operate in anyappropriate wireless network(s). Wireless network 105 may include one ormore mobile devices, such as, for example, User Equipment (UEs) 150-1and 150-2 (as used herein, collectively referred to as “UE 150” andindividually as “UE 150-x”). Wireless network 105 may include an evolvedPacket Core (ePC) 110, and an evolved Universal MobileTelecommunications System (UMTS) Terrestrial Radio Access Network(eUTRAN) 107.

Wireless network 105 may further include one or more devices that arephysical and/or logical entities interconnected via standardizedinterfaces. Wireless network 105 provides wireless packet-switchedservices and wireless IP connectivity to mobile devices to provide, forexample, data, voice, and/or multimedia services. The ePC 110 mayfurther include a mobility management entity (MME) 118, a servinggateway (SGW) device 112, a packet data network (PDN) gateway (PGW) 114,a Policy and Charging Rules Function (PCRF) 116, and a home subscriberserver (HSS) 120. The eUTRAN 107 may further include one or basestations, such as, for example, eNodeBs 140. It is noted that FIG. 1depicts a representative networking system 100 with exemplary componentsand configuration shown for purposes of explanation. Other embodimentsmay include additional or different network entities in alternativeconfigurations than which are exemplified in FIG. 1.

Further referring to FIG. 1, each eNodeB 140 may include one or moredevices and other components having functionality that allow UE 150 towirelessly connect to eUTRAN 107. eNodeB 150 may interface with ePC 110via a S1 interface, which may be split into a control plane S1-Cinterface 130 and a data plane S1-U interface 132. S1-C interface 130may interface with MME device 118. S1-C interface 130 may beimplemented, for example, with a protocol stack that includes a NetworkAccess Server (NAS) protocol and/or Stream Control Transmission Protocol(SCTP). S1-U interface 132 may interface with SGW 112 and may beimplemented, for example, using a General Packet Radio Service TunnelingProtocol version 2 (GTPv2). eNodeB 140 may communicate with othereNodeBs via an X2 interface (not shown). The X2 interface may beimplemented, for example, with a protocol stack that includes an X2application protocol and SCTP.

MME device 118 may implement control plane processing for wirelessnetwork 105. For example, MME device 118 may implement tracking andpaging procedures for UE 150, may activate and deactivate bearers for UE150, may authenticate a user of UE 150, and may interface to non-LTEradio access networks. A bearer may represent a logical channel withparticular QoS requirements, as will be discussed in more detail below.MME device 118 may also select a particular SGW 112 for a particular UE150. A particular MME device 118 may interface with other MME devices(not shown) in ePC 110 and may send and receive information associatedwith UEs, which may allow one MME device to take over control planeprocessing of UEs serviced by another MME device, if the other MMEdevice becomes unavailable.

SGW 112 may provide an access point to and from UE 150, may handleforwarding of data packets for UE 150, and may act as a local anchorpoint during handover procedures between eNodeBs 140. SGW 112 mayinterface with PGW 114 through an S5/S8 interface 122. S5/S8 interface122 may be implemented, for example, using GTPv2.

PGW 114 may function as a gateway to WAN 160 through a SGi interface134. WAN 160 may include, for example, an IP Multimedia Subsystem (IMS)network, which may provide voice and multimedia services to UE 140,based on Session Initiation Protocol (SIP). A particular UE 150, whileconnected to a single SGW 112, may be connected to multiple PGWs 114,one for each packet network with which UE 150 communicates.

PCRF 116 provides policy control decision and flow based chargingcontrol functionalities. PCRF 116 may provide network control regardingservice data flow detection, gating, QoS and flow based charging, etc.PCRF 116 may determine how a certain service data flow shall be treated,and may ensure that user plane traffic mapping and treatment is inaccordance with a user's subscription profile. PCRF 116 may communicatewith PGW 114 using a Gx interface 124. Gx interface 124 may beimplemented, for example, using a Diameter protocol.

MME device 118 may communicate with SGW 112 through an S11 interface126. S11 interface 126 may be implemented, for example, using GTPv2. S11interface 126 may be used to create and manage a new session for aparticular UE 150. S11 interface 126 may be activated when MME device118 needs to communicate with SGW 112, such as when the particular UE150 attaches to ePC 110, when bearers need to be added or modified foran existing session for the particular UE 150, when a connection to anew PGW 114 needs to created, or during a handover procedure (e.g., whenthe particular UE 150 needs to switch to a different SGW 112).

HSS device 120 may store information associated with UEs 150 and/orinformation associated with users of UEs 150. For example, HSS device120 may store user profiles that include authentication and accessauthorization information. MME device 118 may communicate with HSSdevice 120 through an S6a interface 128. S6a interface 128 may beimplemented, for example, using a Diameter protocol.

Content providers 170 may be hosted on any type of web server, mediarepository, streaming source, etc., that can provide UE 150 with contentwhich is requested by the user. Content providers 170 may provide anyform of media, text, audio, image, video, etc., which can be requestedby the user through UE 150. Alternatively, content source may be, orprovide a connection to, another communications provider (e.g., otherwireless carrier, OTT service, etc.), and thus provide UE 150 withvoice, text, and/or video communications with other users of network100.

Wide Area Network 160 may include any type wired or wireless networkcovering larger areas. For example, WAN 160 may include a metropolitanarea network (MAN), a Public Switched Telephone Network (PSTN), an adhoc network, an intranet, the Internet, a fiber optic-based network, awireless network, and/or a combination of these or other types ofnetworks. WAN 160 may be an IP based network or utilize MultiProtocolLabel Switching (MPLS), and may include a mesh network (e.g., IEEE801.11s) and/or or a WiMAX IEEE 802.16. WAN 160 may include one or morecircuit-switched networks and/or packet-switched networks.

Further referring to FIG. 1, multiple elements in ePC 110 performvarious functions which for implementing QoS and policy management. Asnoted above, PCRF 116 may be the policy server in ePC 110. PCRF 116 maytake the available network information and operator-configured policiesto create service session-level policy decisions. The decisions, knownas Policy and Charging Control (PCC) rules, are forwarded to a policyand charging enforcement function (PCEF) (not shown) located in PGW 114.The PCEF enforces policy decisions by establishing bearers, mappingservice data flows to bearers, and performing traffic policing andshaping. In one example, PGW 114 maps bearers to the underlyingtransport network. The transport network will typically be Ethernetbased, and may use MPLS. The transport may not be aware of the bearerconcept and will use standard IP QoS techniques, such as DiffServ.ENodeB 140 plays a role in end-to-end QoS and policy enforcement, andperforms uplink and downlink rate policing, as well as schedulingresource blocks which are transmitted over the wireless channel. EnodeB140 may use Allocation and Retention Policy (ARP) when allocating bearerresources. The effectiveness of resource block scheduling algorithms ineNodeB's 140 can have a significant impact on service quality andoverall network performance. UE 150 may also perform functionality whichimpacts policy in the uplink direction, as it performs the initialmapping of service data flows to bearers.

While FIG. 1 shows exemplary components of network 100, in otherimplementations, network 100 may include fewer components, differentcomponents, differently arranged components, or additional componentsthan depicted in FIG. 1. Additionally or alternatively, one or morecomponents of network 100 may perform functions described as beingperformed by one or more other components.

FIG. 2 is a block diagram showing exemplary components of a base station200 (e.g., eNodeB 140) according to an embodiment. As shown in FIG. 1,base station 200 may include a processing unit 210, a memory 220, a userinterface 230, a communication interface 240, an antenna assembly 250,and a network interface 260.

Processing unit 210 may include one or more processors, microprocessors,application specific integrated circuits (ASICs), field programmablegate arrays (FPGAs), and/or other processing logic. Processing unit 210may control operation of base station 200 and its components.

Memory 220 may include a random access memory (RAM) or another type ofdynamic storage device, a read only memory (ROM) or another type ofstatic storage device, a removable memory card, and/or another type ofmemory to store data and instructions that may be used by processingunit 210.

User interface 230 may include mechanisms for inputting information tobase station 200 and/or for outputting information from base station200. Examples of input and output mechanisms might include a speaker toreceive electrical signals and output audio signals; a microphone toreceive audio signals and output electrical signals; buttons (e.g., ajoystick, control buttons, a keyboard, or keys of a keypad) and/or atouchscreen to permit data and control commands to be input into basestation 200; a display, such as an Liquid Crystal Display (LCD), tooutput visual information; and/or any other type of input or outputdevice. In some embodiments, base station 200 may be managed remotelyand may not include user interface 230. In other words, base station 200may be “headless” and may not include an input device and/or an outputdevice.

Communication interface 240 may include one or more Radio Frequency (RF)transceivers that enable base station 200 to communicate with mobiledevices via wireless communications. An RF transceiver may include an RFtransmitter that receives signals to be transmitted wirelessly andperforms signal processing on the signals before providing the signalsto antenna assembly 250, and an RF receiver that receives signals fromantenna assembly 250 and performs signal processing on the receivedsignals before providing the received signals to processing unit 210.For example, the RF transceiver may perform analog-to-digital anddigital-to-analog conversion, modulation and demodulation, up-conversionand down-conversion, and/or amplification of signals.

Antenna assembly 250 may include one or more antennas to transmit and/orreceive RF signals over the air. Antenna assembly 250 may, for example,receive RF signals from communication interface 240 and transmit thesignals over the air and receive RF signals over the air and providethem to communication interface 240.

Network interface 260 may include a logical component that includesinput and/or output ports, input and/or output systems, and/or otherinput and output components that facilitate the transmission of data toother devices via a backhaul link. For example, network interface 260may include a network interface card (e.g., Ethernet card) for wiredcommunications and/or a wireless network interface (e.g., a WiFi) cardfor wireless communications. Network interface 260 may also include auniversal serial bus (USB) port for communications over a cable, aBluetooth™ wireless interface, a radio-frequency identification (RFID)interface, a near-field communications (NFC) wireless interface, and/orany other type of interface that converts data from one form to anotherform.

As described herein, base station 200 may perform certain operations inresponse to processing unit 210 executing software instructionscontained in a computer-readable medium, such as memory 220. Acomputer-readable medium may be defined as a non-transitory memorydevice. A non-transitory memory device may include memory space within asingle physical memory device or spread across multiple physical memorydevices. The software instructions may be read into memory 220 fromanother computer-readable medium or from another device viacommunication interface 240. The software instructions contained inmemory 220 may cause processing unit 210 to perform processes that willbe described later. Alternatively, hardwired circuitry may be used inplace of, or in combination with, software instructions to implementprocesses described herein. Thus, implementations described herein arenot limited to any specific combination of hardware circuitry andsoftware.

Although FIG. 2 shows example components of base station 200, in otherimplementations, base station 200 may include fewer components,different components, differently arranged components, or additionalcomponents than those depicted in FIG. 2. Additionally or alternatively,one or more components of base station 200 may perform the tasksdescribed as being performed by one or more other components of basestation 200.

FIG. 3 is a block diagram showing exemplary components of a mobiledevice 300 (e.g., UE 150) according to an embodiment. Mobile device 300may include any mobile communication device configured to communicatewith base station 200 via wireless signals. For example, mobile device300 may include a portable communication device (e.g., a mobile phone, asmart phone, a phablet device, a global positioning system (GPS) device,and/or another type of wireless device); a telephone terminal; apersonal computer or workstation; a server device; a laptop, tablet, oranother type of portable computer; a media playing device; a portablegaming system; and/or any type of mobile device with wirelesscommunication capability.

Mobile device 300 may include a bus 310, a processor 315, memory 320, aread only memory (ROM) 325, a storage device 330, one or more inputdevice(s) 335, one or more output device(s) 340, a communicationinterface 345, and Secure Element (SE) 355. Bus 310 may include a paththat permits communication among the elements of mobile device 300.

Processor 315 may include a processor, microprocessor, or processinglogic that may interpret and execute instructions. Memory 320 mayinclude a random access memory (RAM) or another type of dynamic storagedevice that may store information and instructions for execution byprocessor 315. ROM 325 may include a ROM device or another type ofstatic storage device that may store static information and instructionsfor use by processor 315. Storage device 330 may include a magneticand/or optical recording medium and its corresponding drive.

Input device(s) 335 may include one or more mechanisms that permit anoperator to input information to mobile device 300, such as, forexample, a keypad or a keyboard, a microphone, voice recognition,components for a touchscreen, and/or biometric mechanisms, etc. Outputdevice(s) 340 may include one or more mechanisms that output informationto the operator, including a display, a speaker, etc. Communicationinterface 345 may include any transceiver mechanism that enables mobiledevice 105 to communicate with other devices and/or systems. Forexample, communication interface 345 may include mechanisms forcommunicating with another device or system via a network, such aswireless network 300.

Secure Element (SE) 355 may be inserted into a secure element interface(I/F) (e.g., a smart card or Subscriber Identifier Module (SIM) cardinterface) of mobile device 300. SE 355 is a tamper-resistant platform(e.g., a single-chip secure microcontroller) capable of securely hostingapplications and their associated confidential and/or cryptographic data(e.g., key management) in accordance with the rules and securityrequirements set forth by a set of trusted authorities. SE 355 maysecurely store applications and data to permit mobile device 300 toperform trusted exchanges with other network entities. The secureinformation stored in SE 355 may be managed in accordance with rules andsecurity requirements provided by established trusted authorities. SE355 may provide the security and confidentiality required to performvalidation of a user's identity to the network 100. SE 355 may include,for example, a Universal Integrated Circuit Card (UICC), a removableuser identity card (R-UIM), a subscriber identity module (SIM), auniversal subscriber identity module (USIM), or an Internet Protocol(IP) multimedia services identity module (ISIM).

Mobile device 300 may perform certain operations or processes, as may bedescribed in detail below. Mobile device 300 may perform theseoperations in response to processor 315 executing software instructionscontained in a computer-readable medium, such as memory 320. Acomputer-readable medium may be defined as a physical or logical memorydevice. A logical memory device may include memory space within a singlephysical memory device or spread across multiple physical memorydevices. The software instructions may be read into memory 320 fromanother computer-readable medium, such as storage device 330, or fromanother device via communication interface 345. The softwareinstructions contained in memory 320 may cause processor 315 to performoperations or processes that will be described in detail with respect toFIG. 9. Alternatively, hardwired circuitry may be used in place of or incombination with software instructions to implement processes consistentwith the principles of the embodiments. Thus, exemplary implementationsare not limited to any specific combination of hardware circuitry andsoftware.

The configuration of components of mobile device 300 illustrated in FIG.3 is for illustrative purposes only. It should be understood that otherconfigurations may be implemented. Therefore, mobile device 300 mayinclude additional, fewer and/or different components than thosedepicted in FIG. 3.

FIG. 4 is a block diagram showing exemplary components of a networkelement 400, such as, for example, a PCRF 116, according to anembodiment. Network element 400 may include a bus 410, a processor 420,a memory 430, mass storage 440, an input device 450, an output device460, and a communication interface 470.

Bus 410 includes a path that permits communication among the componentsof network element 400. Processor 420 may include any type ofsingle-core processor, multi-core processor, microprocessor, latch-basedprocessor, and/or processing logic (or families of processors,microprocessors, and/or processing logics) that interprets and executesinstructions. In other embodiments, processor 420 may include anapplication-specific integrated circuit (ASIC), a field-programmablegate array (FPGA), and/or another type of integrated circuit orprocessing logic. For example, processor 420 may be an x86 based CPU,and may use any operating system, which may include varieties of theWindows, UNIX, and/or Linux. Processor 420 may also use high-levelanalysis software packages and/or custom software written in anyprogramming and/or scripting languages for interacting with othernetwork entities are communicatively coupled to network 100.

Memory 430 may include any type of dynamic storage device that may storeinformation and/or instructions, for execution by processor 420, and/orany type of non-volatile storage device that may store information foruse by processor 420. For example, memory 430 may include a RAM oranother type of dynamic storage device, a ROM device or another type ofstatic storage device, and/or a removable form of memory, such as aflash memory. Mass storage device 440 may include any type of on-boarddevice suitable for storing large amounts of data, and may include oneor more hard drives, solid state drives, and/or various types of (RAID)arrays. For an advertising server, mass storage device 440 would besuitable for storing files associated sponsor advertising content,databases storing information regarding non-subscription users receivingadvertising content, access parameters for non-subscription users, andinformation which may be used for analytics.

Input device 450, which may be optional, can allow an operator to inputinformation into network element 400, if required. Input device 450 mayinclude, for example, a keyboard, a mouse, a pen, a microphone, a remotecontrol, an audio capture device, an image and/or video capture device,a touch-screen display, and/or another type of input device. In someembodiments, network element 300 may be managed remotely and may notinclude input device 450. Output device 460 may output information to anoperator of network element 400. Output device 460 may include a display(such as an LCD), a printer, a speaker, and/or another type of outputdevice. In some embodiments, network element 400 may be managed remotelyand may not include output device 460.

Communication interface 470 may include a transceiver that enablesnetwork element 400 to communicate within network 100 with other devicesand/or systems. The communications interface 470 may be configured forwireless communications (e.g., RF, infrared, and/or visual optics,etc.), wired communications (e.g., conductive wire, twisted pair cable,coaxial cable, transmission line, fiber optic cable, and/or waveguide,etc.), or a combination of wireless and wired communications.Communication interface 470 may include a transmitter that convertsbaseband signals to RF signals and/or a receiver that converts RFsignals to baseband signals. Communication interface 470 may be coupledto one or more antennas for transmitting and receiving RF signals.Communication interface 470 may include a logical component thatincludes input and/or output ports, input and/or output systems, and/orother input and output components that facilitate thetransmission/reception of data to/from other devices. For example,communication interface 470 may include a network interface card (e.g.,Ethernet card) for wired communications and/or a wireless networkinterface (e.g., a WiFi) card for wireless communications. Communicationinterface 470 may also include a universal serial bus (USB) port forcommunications over a cable, a Bluetooth® wireless interface, an RFIDinterface, an NFC wireless interface, and/or any other type of interfacethat converts data from one form to another form.

As described below, network element 400 may perform certain operationsrelating to server (e.g., PCRF, MME) and/or gateway operations whenembodied as a gateway (e.g., SGW 112 and/or PGW 114), and/or providinguser subscription and service information when embodied as an HSS 120.Network element 400 may perform these operations in response toprocessor 420 executing software instructions contained in acomputer-readable medium, such as memory 430 and/or mass storage 440.The software instructions may be read into memory 430 from anothercomputer-readable medium or from another device. The softwareinstructions contained in memory 430 may cause processor 420 to performprocesses described herein, such as, for example, process 700 depictedin FIG. 7. Alternatively, hardwired circuitry may be used in place of,or in combination with, software instructions to implement processesdescribed herein. Thus, implementations described herein are not limitedto any specific combination of hardware circuitry and software.

Although FIG. 4 shows exemplary components of network element 400, inother implementations, network element 400 may include fewer components,different components, additional components, or differently arrangedcomponents than depicted in FIG. 4.

FIG. 5A is a block diagram illustrating the operation of an exemplaryscheduler 500 which allocates resources based on requested bandwidth.The embodiment illustrated in FIG. 5A schedules resource blocks within asingle bearer for a given mobile device (e.g., UE 150). Scheduler 500may reside in a base station (e.g., eNodeB 140) and schedule resourceblocks for downlink transmissions to one or more mobile devices over awireless channel. Scheduler 500 may include resource block schedulinglogic 505 and Queue Server 520. These functional blocks may beimplemented in software which executes on a processor (e.g., processingunit 210), or using dedicated hardware, or a combination thereof.

In an embodiment, a resource block may be a data structure that can besubdivided into resource elements which are organized in terms of bothtime and frequency. Each resource element may represent one orthogonalfrequency division multiplexed (OFDM) sub-carrier during one OFDM symbolinterval, where a symbol in each resource element represents apre-defined number of bits based upon their symbol modulation (e.g.,QPSK, 16-QAM, 64-QAM, etc.). The information density of a resource blockcan depend upon the attributes of the wireless channel. For example,under channel conditions having high signal-to-noise ratio, each of thesymbols in the resource blocks will represent more bits-per-symbol.Thus, the information density within each resource block increases aswireless channel conditions improve. The information density may bereflected in a parameter referred to as the Modulation Coding Scheme(MCS) value which may be determined by eNodeB 140 using, for example,estimates of wireless channel conditions based on pilot signalsexchanged with the UE 150. Moreover, as bandwidth of the wirelesschannel increases, more resource blocks may be sent over the downlink toUE 150.

According to an embodiment, LTE provides standards outlining how toprovide transmission paths between UE 150 and wide area network 160 withwell-defined QoS. This may be established using a “bearer model,” wherea bearer is a basic traffic separation element that enables differenttreatment for traffic with differing QoS requirements. Bearers canprovide logical, edge-to-edge transmission paths with defined a QoSbetween UE 150 and PGW 114. Each bearer may be associated with a set ofQoS parameters that describe properties of the transport channel,including packet delays, bit rates, packet loss, bit error rate, andscheduling policy in eNodeB 140. A bearer may support multipleApplication Data Flows (ADFs) which have a common QoS parameters, butcan have different bandwidth requirements. A bearer may have a number ofdifferent QoS parameters which vary depending upon whether the bearersupports a real-time (e.g., GBR) or a best effort service (e.g.,non-GBR). The parameters for non-GBR bearers may include QoS ClassIndicator (QCI) and Allocation and Retention Priority (ARP). The QCI mayspecify the treatment of packets received on a specific bearer. Packetforwarding of traffic traversing a bearer is handled by each networkelement (e.g., PGW 114, SGW 112, eNodeB 140). QCI values arestandardized into a number of different types, and can impactnon-specific parameters, such as link layer configuration, scheduling,and queue management. LTE networks have the ability to drop or downgradelower-priority bearers in situations where the network becomescongested. Each bearer may have an associated allocation and retentionpriority (ARP) which may be used in bearer establishment, and which maybecome relevant during handoff situations when UE 150 transitions overto another eNodeB. The network may use ARP when determining whether toestablish new dedicated bearers.

Scheduler 500 shows two different bearers, Bearer 1 and Bearer 2, whichsupport multiple application data flows for a single UE 150. Bearer 1,which has a QCI value of 7, has higher priority than Bearer 2, which hasa QCI value of 9. Accordingly, based on conventional QoS techniques, theApplication Data Flows (ADFs) in Bearer 1 (ADF 1, ADF 2, and ADF 3) willhave greater priority than the ADFs being serviced by Bearer 2 (ADF 4and ADF 5). However, with conventional scheduling, ADFs within a singlebearer are not scheduled according to each ADF's resource requirements(e.g., bandwidth), thus some ADFs, such as those with higher bandwidthrequirements, may not receive the resources required for the properoperation of their associated applications.

Further referring to FIG. 5A, according to one embodiment, finergranularity prioritization within each bearer may be performed byscheduler 500 based on the requested bandwidth associated with each ADFwithin that bearer. As shown in FIG. 5A, the requested bandwidth foreach ADF is pictorially represented as being proportional to thethickness of the “tubes” representing each ADF. The actual requestedbandwidth values are provided to resource block scheduling logic 505,along with the each ADF from both Bearer 1 and Bearer 2. Accordingly,ADF 2 has a higher requested bandwidth than ADF 1, and ADF 1 has ahigher requested bandwidth than ADF 3. Thus, resource block schedulinglogic 505 will take into account the requested bandwidth for each ADFwithin Bearer 1, and assign higher priorities to ADFs requesting morebandwidth. So for example, for ADF 2, resource block scheduling logic505 will allocate the largest amount of resources blocks 510. For ADF 1,resource block scheduling logic 505 will allocate the second largestnumber of resource blocks 512. ADF 3, having the lowest requestedbandwidth, will receive the smallest number of resource blocks 514. ForBearer 2, ADF 5 will be allocated the larger portion of resource blocks516, and ADF 4 will be allocated the smaller portion of resource blocks518. For this embodiment, the allocation of resource blocks based onrequested bandwidth is scheduled within each bearer. That is, eachbearer will have a certain number of resource blocks allocated to itbased on the bearer's QCI value. Resource block scheduling logic 505refines the allocation of resource blocks allocated to each bearer overeach ADF based on the requested bandwidth for each application. Theembodiment thus provides “application fairness” across each bearer foreach UE that has a wireless channel established with eNodeB 140. Onceeach bearer's ADFs are allocated resources based on requested bandwidth,the resource block scheduling logic 505 may provide the scheduledresource blocks to Queue Server 520 where they are buffered andappropriately scheduled based on their QCI into prioritized applicationdata streams for transmission over the wireless channel to UE 150.

In another embodiment, if the resource block scheduling logic 505determines there are not enough resource blocks to properly allocate toan ADF which has high bandwidth requirements, the scheduler may chooseto service lower priority ADFs first to get them out of the queue, andthen try to service the ADF having high bandwidth requirements once anadequate number of resource blocks become available.

FIG. 5B is a block diagram illustrating the operation of an exemplaryscheduler 500 which allocates resources based wireless channelconditions. The wireless conditions may be empirically determined by theeNodeB 140, which may be used to set a Modulation Coding Scheme (MCS)for determining the symbol coding density of the application data flows.Accordingly, in an embodiment, the MCS values may be used to infer thequality of the wireless channel.

In this embodiment, resource block scheduling logic 505 may allocateblocks differently across two different UEs 150-1, 150-2, based on thequality of their respective wireless channels to eNodeB 140. Therefore,in this embodiment, the resource blocks across different UEs 150 may beallocated differently even if the ADFs for each UE are assigned tobearers have the same QCI value. For example, as shown in FIG. 5B,Bearer 3 has a QCI value of 9, and supports ADF 6 and ADF 7, where ADF 7has a higher requested bandwidth than ADF 6. Accordingly, with respectto Bearer 3, ADF 7 will be prioritized above ADF 6, and thus beallocated with more resource blocks 530. ADF 6 will be allocated withlesser priority using fewer resource blocks 532. Similarly, Bearer 4 hasa QCI value of 9, and supports ADF 8 and ADF 9, where ADF 9 has a higherrequested bandwidth than ADF 8. Thus, with respect to Bearer 4, ADF 9will be prioritized above ADF 8, and therefore be allocated with moreresource blocks 534. ADF 8 will be allocated with lower priority usingfewer resource blocks 536.

In an embodiment, resource blocks may be scheduled differently among thedifferent UEs 150-1, 150-2, even though Bearer 3 and Bearer 4 have thesame QCI value. In one embodiment, more blocks will be allocated to theADFs associated with the UE having poorer channel conditions (e.g., UE150-2), and less blocks will be allocated to the ADFs associated withthe UE (e.g., UE 150-1) having better channel conditions. As notedabove, the information density of resource blocks will vary dependingupon the wireless channel conditions associated with each UE. For goodwireless conditions, more bits may be transferred in each resource blockthan when wireless conditions are bad. Thus, in order to promotefairness among applications across different UEs 150 having variedwireless channel conditions, the number of resource blocks allocated toADFs can vary based on the quality of the wireless channel between UEs150 and eNodeB 140.

For example, as can be seen in FIG. 5B, ADF 9, which is associated withUE 150-2 having poor wireless channel conditions, is allocated moreresource blocks 534 than ADF 7. ADF 7 is allocated fewer resource blocks530 because UE 150-1 is associated with good wireless channelconditions. The difference in the number of blocks can be based on thedifferences in information density, and the blocks can be allocated sothat the number of bits transferred for each UE 150 is approximately thesame. The MCS may be used as an indicator of the quality of the wirelesschannel, since the MCS can be determined at eNodeB 114 through analyzingpilot signals transmitted by each UE 150-1, 150-2. Once resource blockscheduling logic 505 allocates the resource blocks for the ADFs inBearer 3 and Bearer 4, the ADFs may then be provided to Queue Server 520so the allocated resources blocks may be scheduled for subsequenttransmission to each UE 150 over the downlink wireless channel.

FIG. 6 is a signal flow diagram depicting exemplary messages exchangedbetween various networking entities in network 100. In an embodiment, UE150 may initially launch an application (612) which requests anapplication data flow from one or more content providers 170. UE 150 maythen send a connection request to PCRF 116 (602), which includes anapplication category and a requested bandwidth. The connection requestmay pass through eNodeB 140, Serving Gateway 112, and PDN Gateway 114before arriving at PCRF 116. The requested bandwidth may be a minimumbandwidth of the application data flow that is required for properexecution of the application. The application category may, for example,identify the application to PCRF 116 for determining QoS prioritization(e.g., determine a QCI value). This can be accomplished by providinginformation which is commonly referred to as the “5-tuple.” The 5-tuplemay include: the source IP address, the destination IP address, thesource port number, the destination port number, and the protocolinformation of the application data stream.

Based upon the 5-tuple and using available network information and/oroperator configured policies, PCRF 116 may determine a policy for theapplication data flow associated with the application (614). Forexample, the policy may further include QCI configuration informationwhich may be pre-provisioned in PCRF 116 (e.g., by one or more contentproviders and/or a network operator). In one implementation, the QCIconfiguration information may define priorities associated withsubscribers of the IP wireless access network. For example, the QCIconfiguration information may include information associated withsubscribers (e.g., users of UEs 150) of content provider(s) 170 and/ordata services providers. For example, the QCI configuration informationmay include, for each application and/or subscriber, a particular QCIvalue.

Once the policy is determined by PCRF 116, the policy for theapplication data flow may be provided to PDN Gateway 114 (604). PDNGateway 114 may map the application data flow to a particular bearerbased on the determined policy, and further provide a bandwidthdesignation based on the requested bandwidth (616). As noted above withregards to FIGS. 5A and 5B, the bearer can be associated with aparticular QCI value, and carry multiple application data flows. PDNGateway 114 may send a Bearer ID and the bandwidth designation to MME118 through Serving Gateway 112 (606). MME 118 may provide a UE ID,along with the Bearer ID and a Socket Connection to eNodeB 140 (607). Inan embodiment, the Socket Connection may be based on bandwidthdesignation, and thus be associated with a particular bandwidth for theapplication data flow within the bearer designated by the Bearer ID. Inaddition, eNodeB 140 may receive the application data flow from PDNGateway 114 through Serving Gateway 112 (608). Using the receivedinformation, eNodeB 140 may schedule resource blocks based on both theBearer ID and the Socket Connection which is indicative of the requestedbandwidth. As will be described in more detail below in regards to FIG.8, for application data flows within the bearer associated with theBearer ID, eNodeB 140 will provide finer granularity QoS prioritizationbased on the requested bandwidth for each application data flow in thebearer associated with the Bearer ID. UE 150 may receive the scheduledapplication data flows from eNodeB 140 (610).

FIG. 7 is a flow chart showing an exemplary process 700 for providing aQuality of Service (QoS) policy based on bandwidth. Process 700 may beperformed on a network device, such as a server or a PCRF 116. Thenetwork device may initially receive a connection request which mayinclude a requested bandwidth for an application launched by UE 150(710). In an embodiment, the connection request may occur during anattachment procedure. The requested bandwidth may include a minimumbandwidth required for the operation of the application. The connectionrequest may also include an application category which may be specifiedas a 5-tuple as noted above in regards to the description of FIG. 6. The5-tuple may include a source Internet Protocol (IP) address, adestination IP address, a source port number, a destination port number,and a protocol identification.

The network device may determine a policy for an application data flowassociated with the application based on the connection request (720).The policy may include a QoS Class Indicator (QCI) which is based uponat least one of a profile of the application or a subscription profileassociated with a mobile device which hosts the application.

The network device may assign a bandwidth designation for the determinedpolicy to the application data flow (730), where the bandwidthdesignation may be based on the requested bandwidth. In an embodiment,the bandwidth designation may include a designation and/or assignment ofa socket connection within a bearer. The network device may then providethe policy and the bandwidth designation for assignment to a bearer(740). The policy and bandwidth designation may be provided to a Policyand Charging Enforcement Function (PCEF) within PGW 114.

FIG. 8 is a flow chart showing an exemplary process 800 for Quality ofService (QoS) resource allocation based on bandwidth. Process 800 may beperformed by a base station, such as, for example, an eNodeB 140. In anembodiment, an eNodeB 140 may initially receive an Application Data Flow(ADF) (810). The ADF may originate at one or more content providers 170,and can be provided by PGW 114 in wireless network 105. The ADF isprovided in response to a request by an application operating on amobile device 150. ENodeB 140 may then receive a bandwidth designationassociated with the application data flow (820). In an embodiment, thebandwidth designation may be provided as a socket in a bearer. ENodeB140 may allocate resource blocks to the application data flow, where theallocation may be based on the bandwidth designation (830). Theallocation may be performed by scheduler 500. The bandwidth designationmay be a minimum bandwidth required for operation of the application.ENodeB 140 may schedule the allocated resource blocks (840), and thentransmit the scheduled resource blocks to a UE 150 (850).

In an embodiment, eNodeB 140 may utilize information regarding awireless channel condition for the UE 150 associated with theapplication, and allocate resource blocks based on the wireless channelcondition. For example, the Modulation Coding Scheme (MCS) may be usedas an indicator of the quality of the wireless channel, since the MCScan be determined at eNodeB 114 through analyzing pilot signalstransmitted by each UE 150. The difference in the number of blocks canbe based on the differences in information density, and the blocks canbe allocated so that the number of bits transferred for each UE 150 isapproximately the same.

FIG. 9 is a flowchart showing an exemplary process 900 for receivingresource blocks allocated based on bandwidth. In an embodiment, process900 may be performed within a UE 150, and starts when UE 150 launches anapplication (910). The application may require data from one or morecontent provider 170 over wide area network 160. Accordingly, UE 150 mayprovide a connection request which includes an application category anda requested bandwidth (920). The application category may be provided asa 5-tuple as described above in regards to FIG. 6. The requestedbandwidth may be a minimum bandwidth required for proper operation ofthe launched application. The UE 150 may receive allocated resourceblocks from eNodeB 140 which may be allocated to an Application DataFlow (ADF) based on a bandwidth designation (930). The bandwidthdesignation may be based on the requested bandwidth. In one embodiment,the bandwidth designation may include a socket within a bearer having aprescribed bandwidth.

The foregoing description of implementations provides illustration anddescription, but is not intended to be exhaustive or to limit theinvention to the precise form disclosed. Modifications and variationsare possible in light of the above teachings or may be acquired frompractice of the invention. For example, while series of messages and/orblocks have been described with regard to FIGS. 6-9, the order of themessages and/or blocks may be modified in other embodiments. Further,non-dependent messaging and/or processing blocks may be performed inparallel.

Certain features described above may be implemented as “logic” or a“unit” that performs one or more functions. This logic or unit mayinclude hardware, such as one or more processors, microprocessors,application specific integrated circuits, or field programmable gatearrays, software, or a combination of hardware and software.

In the preceding specification, various preferred embodiments have beendescribed with reference to the accompanying drawings. It will, however,be evident that various modifications and changes may be made thereto,and additional embodiments may be implemented, without departing fromthe broader scope of the invention as set forth in the claims thatfollow. The specification and drawings are accordingly to be regarded inan illustrative rather than restrictive sense.

The terms “comprises” and/or “comprising,” as used herein specify thepresence of stated features, integers, steps or components but does notpreclude the presence or addition of one or more other features,integers, steps, components, or groups thereof. Further, the term“exemplary” (e.g., “exemplary embodiment,” “exemplary configuration,”etc.) means “as an example” and does not mean “preferred,” “best,” orlikewise.

No element, act, or instruction used in the description of the presentapplication should be construed as critical or essential to theinvention unless explicitly described as such. Also, as used herein, thearticle “a” is intended to include one or more items. Further, thephrase “based on” is intended to mean “based, at least in part, on”unless explicitly stated otherwise.

What is claimed is:
 1. A method, comprising: receiving, at a basestation, an application data flow associated with a mobile device;receiving, at the base station, a bandwidth designation for theapplication data flow; determining, at the base station, a wirelesschannel condition associated with the mobile device; allocating, at thebase station, resource blocks to the application data flow based on thewireless channel condition and the bandwidth designation; scheduling, atthe base station, the allocated resource blocks; and transmitting, fromthe base station, the scheduled resource blocks to the mobile device. 2.The method of claim 1, wherein allocating resource blocks based on thewireless channel condition further comprises: increasing a number ofresource blocks allocated when the wireless channel condition hasdeclined, and decreasing the number of resource blocks allocated whenthe wireless channel condition has improved.
 3. The method of claim 1,wherein allocating resource blocks based on the wireless channelcondition further comprises: allocating the resource blocks based ondifferences in information density within the resource blocks, so that anumber of bits transferred across the wireless channel is approximatelythe same over varying wireless channel conditions.
 4. The method ofclaim 1, wherein determining the wireless channel condition furthercomprises: ascertaining a modulation coding scheme for the mobiledevice.
 5. The method of claim 4, wherein ascertaining the modulationcoding scheme comprises: determining a symbol coding density of theapplication data flow.
 6. The method of claim 1, wherein the bandwidthdesignation comprises a socket within a bearer having a designatedbandwidth.
 7. The method of claim 6, wherein the socket is associatedwith a particular bandwidth for the application data flow within thebearer designated by a bearer identifier.
 8. A base station, comprising:a radio frequency interface configured to communicate over a wirelesschannel; an interface configured to communicate with a network; a memoryconfigured to store instructions; and a processor, coupled to the radiofrequency interface, the interface, and the memory, wherein theprocessor is configured to execute the instructions stored in the memoryto: receive an application data flow associated with a mobile device;receive a bandwidth designation for the application data flow; determinea wireless channel condition associated with the mobile device; allocateresource blocks to the application data flow based on the wirelesschannel condition and the bandwidth designation; schedule the allocatedresource blocks; and transmit the scheduled resource blocks to themobile device.
 9. The base station of claim 8, wherein the instructionsto allocate resource blocks based on wireless channel condition furthercause the processor to: increase a number of resource blocks allocatedwhen the wireless channel condition has declined, and decrease a numberof resource blocks allocated when the wireless channel condition hasimproved.
 10. The base station of claim 8, wherein the instructions toallocate resource blocks based on the wireless channel condition furthercause the processor to: allocate the resource blocks based ondifferences in information density within the resource blocks, so thatthe number of bits transferred across the wireless channel isapproximately the same over varying wireless channel conditions.
 11. Thebase station of claim 8, wherein the instructions to determine thewireless channel condition further cause the processor to: ascertain amodulation coding scheme for the mobile device.
 12. The base station ofclaim 11, wherein the instructions to ascertain the modulation codingscheme further cause the processor to: determine a symbol coding densityof the application data flow.
 13. The base station of claim 8, whereinthe bandwidth designation comprises a socket within a bearer having adesignated bandwidth.
 14. The base station of claim 13, wherein thesocket is associated with a particular bandwidth for the applicationdata flow within the bearer designated by a bearer identifier.
 15. Anon-transitory computer-readable medium comprising instructions, which,when executed by a processor, cause the processor to: receive anapplication data flow associated with a mobile device; receive abandwidth designation for the application data flow; determine awireless channel condition associated with the mobile device; allocateresource blocks to the application data flow based on the wirelesschannel condition and the bandwidth designation; schedule the allocatedresource blocks; and transmit the scheduled resource blocks to themobile device.
 16. The non-transitory computer-readable medium of claim15, wherein the instructions to allocate resource blocks based onwireless channel condition further cause the processor to: increase anumber of resource blocks allocated when the wireless channel conditionhas declined, and decrease the number of resource blocks allocated whenthe wireless channel condition has improved.
 17. The non-transitorycomputer-readable medium of claim 15, wherein the instructions toallocate resource blocks based on the wireless channel condition furthercause the processor to: allocate the resource blocks based ondifferences in information density within the resource blocks, so that anumber of bits transferred across the wireless channel is approximatelythe same over varying wireless channel conditions.
 18. Thenon-transitory computer-readable medium of claim 15, wherein theinstructions to determine the wireless channel condition further causethe processor to: ascertain a modulation coding scheme for the mobiledevice.
 19. The non-transitory computer-readable medium of claim 18,wherein the instructions to ascertain the modulation coding schemefurther cause the processor to: determine a symbol coding density of theapplication data flow.
 20. The non-transitory computer-readable mediumof claim 15, wherein the bandwidth designation comprises a socket withina bearer having a designated bandwidth.